208 \n\nSwitches Other Names Description (default)\n--------------------------------------------------------------------------------\n/Count:number /C /Length /L Number of instructions to display (8)\n/EndAddress:expression /E Address at which to stop disassembly \n/CodeBytes:yes/no /B /Bytes Whether to display code bytes (no)\n/Source:yes/no /S Whether to display source code (no)\n/Symbols:ye \n\n\ns/no /N /Names Whether to display symbol names (yes)
209 \n\nNotes:\n* Changing the display of CodeBytes, Source, and Symbols applies to\n future invocations of the Debug.ListDisassembly command.\n
210 Debug.ListDisassembly - displays disassembly
211 (no condition)
216 Unable to go to the breakpoint. %1
222 Unable to set the current program.
224 Unable to set the current thread.
226 Unable to set the current stack frame.
232 This thread has called into a function that cannot be displayed.
236 Module
238 Address
240 Function
252 Index
254 Function
256 Language
257 < More... (The first %1 of %2 items were displayed.) >
264 \n\nSyntax: Debug.ListCallStack [switches]
266 \n\nSwitches Other Names Description (default)\n---------------------------------------------------------------------------------------------\n/Count:number /C Maximum number to display (unlimited)\n/ShowTypes:yes/no /T Whether to display parameter types (yes)\n/ShowNames:yes/no /N Whether to display parameter names (yes)\n/ShowValues:yes/no /V Whether to display \n\n\nparameter values (yes)\n/ShowModule:yes/no /M Whether to display the module name (yes)\n/ShowLineOffset:yes/no /# Whether to display the line offset (no)\n/ShowByteOffset:yes/no /B Whether to display the byte offset (no)\n/ShowLanguage /L Whether to display the language (no)\n/IncludeCallsAcrossThreads /I Whether to include calls to/from other threads (no)
270 Debug.ListCallStack - displays the call stack
272 \n\nNotes:\n* Changes to these settings will apply to future invocations of the ListCallStack command.
500
501 Unable to update the breakpoint.
502 Execution has stopped at the beginning of the program because one or more breakpoints could not be set.
503 An exception containing the specified string was not found.
504 There are no more exceptions containing the specified string.
505 Unable to connect to the machine '%1'. %2
506 Unable to disable all of the breakpoints. %1
507 Unable to attach to the process. %1
508 The debugger cannot display source code or disassembly for the current location where execution has stopped.
509 Error
510 Please enter a named location.
511 The machine cannot be found on the network.
512 Access is denied. Check the DCOM configuration settings for the Machine Debug Manager.
513 A previous expression evaluation is still in progress.
514 Unable to start the Machine Debug Manager on the specified machine.
515 The machine is not currently available on the network.
516 A debugger is already attached.
517 The process does not have sufficient privileges to be debugged.
518 The desktop cannot be debugged.
519 The debugger is not properly installed.
520 Unable to break into the process '%1'. %2
521 Unable to break into the process. %1
522 Unable to detach from the process '%1'. %2
523 Unable to detach from the process. %2
524 Cannot run to the specified location.
525 Unable to evaluate the expression. %1
526 Unable to start program '%1'.\n\n%2
527 Unable to set the next statement to this location. %1
528 Unable to open input file '%1'.
529 Unable to open output file '%1'.
530 The exception name is not valid.
531 Unable to attach to application '%1' (PID: %3) on machine '%2'.\n\nDo you want to continue anyway?
532 Unable to attach to machine '%1'.\n\nDo you want to continue anyway?
533 Unable to debug the process at this time.
534 Unable to execute the statement because the current thread is not executing code.
535 Invalid expression.
536 Unable to restart debugging. %1
537 The specified hit count target is not valid.
538 Unable to set exceptions.
539 Unable to start debugging. A program to debug has not been specified.
540 Please enter a valid file name.
541 Please enter a breakpoint location.
542 Memory could not be displayed for the expression.\n%1
543 The file name must be an absolute path. For example, 'c:\dir\file.ext' or '\\server\share\dir\file.ext'
544 Disassembly cannot be displayed for the source location. %1
545 MSVCMON is not running on the remote machine.
546 The process has been terminated.
547 The IP address for the remote machine is not valid.
548 The remote machine is not responding.
549 The remote machine name is not specified.
550 Other programs cannot be debugged while post-mortem debugging.
551 All of the threads are frozen. Please use the Threads window to unfreeze at least one thread before attempting to step or continue the program.
552 The debugger transport dll cannot be loaded.
553 NatDbgSH.dll cannot be loaded.
554 NatDbgEM.dll cannot be loaded.
555 NatDbgEE.dll cannot be loaded.
556 NatDbgDM.dll cannot be loaded.
557 Output cannot be redirected because the specified file is invalid.
558 Output cannot be redirected because the syntax is incorrect.
559 The remote debugger is not an acceptable version.
560 This is not a valid location for a breakpoint.
561 Some breakpoints could not be deleted and have been disabled instead.
562 No source file
563 Unavailable when debuggee is running.
564 Unavailable when not debugging.
565 Please enter an expression.
566 The specified address cannot be displayed. %1
567 One or more breakpoints could not be deleted.
568 The call stack is not available at this time.
569 The call stack cannot be displayed. %1
570 The call stack is empty.
571 Unable to list programs. %1
572 Unable to list threads. %1
573 Unable to list memory. %1
574 Unable to list registers. %1
575 Unable to set radix.
576 Unable to list disassembly. %1
577 This operation is not supported during post-mortem debugging.
578 The source code cannot be displayed. %1
579 The specified radix is not recognized.
580 Please specify an address.
581 The debugger cannot continue running the program. %1
582 The end address '%1' cannot be evaluated. %2
583 Could not write value to memory
584 The Visual Studio Debugger Proxy service was not running when debugging was started.
585 The expression evaluation took too long.
586 There is no executable code at this location in the source code.
587 The expression cannot be evaluated while in run mode. %1
588 The debugger cannot step program execution. %1
589 Unable to detach from one or more programs. %1
590 Unable to stop debugging. %1
591 The breakpoint could not be set. %1
592 %1 does not support breakpoint conditions.
593 %1 does not support breakpoint hit counts.
594 %1 does not support address breakpoints.
595 Unable to go to the source code of the breakpoint.
596 The expression cannot be evaluated while in design mode.
597 %1 does not support call stack breakpoints.
598 %1 does not support function breakpoints.
599 %1 does not support data breakpoints.
600 Unable to go to the disassembly of this breakpoint.
601 The specified file is an unrecognized or unsupported binary format.
602 %1 does not support disassembly.
603 Disassembly cannot be displayed. %1
605 The current program type does not support disassembly.
606 The specified count is too large. The maximum count is %1.
607 Cannot detach from one or more programs. Terminate them instead?
608 (Disassembly cannot be displayed in run mode.)
609 Unable to connect to the port '%1'. %2
610 The specified address does not exist in disassembly.
611 Cannot detach from one or more programs: %1\n\nTerminate them instead?
612 Step Into Remote Procedure Call
4958 No data available
4959 Debugger Data Changed
4960 Registers
4961 Modules
4963 Name
4964 Address
4965 Path
4966 Order
4967 Version
4968 Information
4969 Program
4970 Executables (*.exe)|*.exe|
4971 Find Program to Debug
4972 Browse for Working Directory
4973 The program specified does not exist or is only a directory. Did you include the full path?
4974 The debug session could not be created. %1
4975 The working directory specified does not exist or is not a directory.
4976 Save Crashdump As
4977 This
4978 Memory Edit
4979 The thread %1 has exited with code %2.
4980 The program '%1' has exited with code %2.\n
4981 Edit-and-Continue will not be supported while debugging. %1
4982 Memory Unreadable
4983 Unable to break execution. %1
4984 There is not a loaded project that can be launched.
4985 An initial stopping location was not found in the program. To stop during program execution, first set a breakpoint and then start running the program.
4986 Register Data
4987 No memory.
4988 Detach from this process
4989 Terminate this process
4990 Unable to terminate process '%1'. %2
4991 Unable to terminate process. %1
4992 Unable to start Just-In-Time debugging. %1
4993 Unknown ExceptionType
4994 Edit and Continue was unable to apply your code changes. %1
4995 JayBaz wants to put a string here someday.
4996 (Hit Ignore to continue anyway.)
4997 Applying Code Changes...
4998 Apply Code Changes succeeded
4999 JayBaz wants to put a string here someday.
5000 Debugging
5001 General
5002 Find Source
5003 Edit and Continue
5004 Native
5005 Edit and Continue
5006 Stale Code
5007 Find Symbol
5008 The option to only stop execution of the current program has been specified. Therefore, the current program cannot be changed.
5009 <Unknown Transport>
5010 P&ort:
5011 &Machine:
5012 This Program Type is required to handle the exception you are debugging and cannot be unselected.
5013 The name of the file entered must match that of the original source file.
5014 '%1' is not a valid working directory.
5015 Cannot find port. Check the remote machine name.
5016 The process has been soft broken.
5017 CPU\nEffective Address
5018 Crashdump Files (*.dmp)|*.dmp|
5019 The minidump reader dll cannot be loaded.
5020 The Visual Studio Debugger Proxy service cannot be used in a Terminal Server session.
5021 The Visual Studio Debugger Proxy service failed to impersonate the current user.
5022 Unable to automatically attach to %1. \n%2
5023 Server side error occurred on sending debug http request.
5024 You do not have permissions to debug the server.
5025 Attempt to send a debugger HTTP request failed.
5026 The project is not configured to be debugged.
5027 <Unknown Module>
5028 Process '%1' is not running on %2.
5029 The expression has not yet been translated to native machine code.
5030 Register Not A Thing
5031 The next statement cannot be changed when stopped at an exception.
5032 There is no MSVCMON on the remote machine running under the current user context.
5033 The switch value '%1' should either be 'Yes' or 'No'.
5034 The switch value '%1' should be a number.
5038 There is no code at the supplied location.
5039 Unable to stop debugging %1. \n%2
5040 The server doesn't support debugging of ASP.NET or ATL Server applications.
5041 The HTTP request resulted in no content being returned.
5042 The next statement cannot be set to another function.
5043 Unable to launch. %1
5044 Session
5045 The file cannot be opened.
5046 This operation will first move to the top frame of the call stack and then move to a different scope. Are you sure?
5047 The debugger is not properly installed on machine '%1'.
5048 <Unknown Error>
5052 Debug Source Files
5053 Debug Symbol Files
5054 Cannot step while in system code on Win9x
12000 The dbgproxy service can be started from a command prompt by entering 'net start dbgproxy'.
12001 Please refresh the process list before attempting another attach.
12002 Please refer to the HTTP debugging topic in the online documentation.
12003 Verify that you are a member of the 'Debugger Users' group on the server.
12004 Please make sure the server is operating correctly. You may also want to refer to the online topic concerning HTTP Debugging.
12005 Verify that either ASP.NET or ATL Server is correctly installed on the server.
12006 For ASP.NET projects, verify that 'debugmode' is set to 'true' in the project file 'config.web'.\n\nFor ATL Server projects, verify that the 'DEBUG' verb is associated with your ISAPI extension.
12007 Possible causes include:\n 1. A debugger is already attached.\n 2. Trying to attach to a remote IIS process. This is currently not supported. To workaround, start without debugging and then attach to remote IIS process in this scenario.
12008 Please verify your JIT settings. [Provide user more details as to what to do here]